-
Notifications
You must be signed in to change notification settings - Fork 46.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conditionally enable profiler component stacks #19396
Conditionally enable profiler component stacks #19396
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit e6e3d8b:
|
Details of bundled changes.Comparing: aec934a...e6e3d8b react-dom
react-art
react-reconciler
ReactDOM: size: 0.0%, gzip: 0.0% Size changes (experimental) |
Details of bundled changes.Comparing: aec934a...e6e3d8b react-art
react-dom
ReactDOM: size: 0.0%, gzip: 0.0% Size changes (stable) |
2eb9a5d
to
2d15507
Compare
2d15507
to
e6e3d8b
Compare
This PR fixes the 300 and 310 errors I've been seeing on Facebook.com (tested with an on-demand just now). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
This PR stacks on top of #19376 and includes only one commit, e6e3d8b
The new component stack approach introduced in #18495 seems to cause bugs (e.g. 1, 2) when used by the new profiler marks (#19376), so this PR moves that part of the profiler behind a feature flag (off by default).
This will enable us to sync the new profiler marks to the new reconciler and let people start using them within Facebook safely, while still enable me to further investigate why the errors are happening. (I've done a www sync of this PR and verified that it fixes the 300 and 310 errors I've been seeing on Facebook.com)
Note that this is a dynamic feature flag, but it's only used once during initialization so it should be okay.